-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spell Checker #44
Spell Checker #44
Conversation
Hey. Looks good. Thanks. I just writen coden too fast too often haha |
But you have to resolve the conflicts and fix the CI before i can merge |
I will rebase when I'm home. |
16a0dd8
to
12890ff
Compare
Great. CI is passing now, Just fix the conflicts then again |
12890ff
to
4240df8
Compare
If you're going to merge other PRs at 6AM my time, and I rebase at 6PM my time, this is going to go on for a while. Feel free to rebase yourself. It's not like these are complex changes. |
Is this ready for merge ? |
I don't see why it wouldn't be. Go ahead when you're ready. |
In taking a look at the project, there are a few typos in type names that potentially cause a lot of churn to fix. It's better to catch them now, than have to touch a thousand files later when
entitiy
is used in a hundred places.Not trying to be a grammar nazi or anything in comments, but type names matter!
I've separated the spell corrections to different commits to minimize the number of files touched by each commit.
If you don't want to have a bunch of commits for spelling mistakes, make sure to commit and squash.